UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

SMTP Maximum Hop Count is not 30.


Overview

Finding ID Version Rule ID IA Controls Severity
V-18688 EMG2-130 Exch2K3 SV-20316r1_rule ECSC-1 Low
Description
E-mail system availability depends in part on best practices strategies for setting tuning configurations. This setting controls the maximum number of hops (E-mail servers traversed) a message may take as it travels to its destination. Part of the original Internet protocol implementation, the hop count limit prevents a message being passed in a routing loop indefinitely. Messages exceeding the maximum hop count are discarded undelivered. Recent studies indicate that virtually all messages can be delivered in fewer than 25 hops, well within the current default of 30. If the hop count is set too low, messages may expire before they reach their destinations. If set too high, an undeliverable message may cycle between servers, raising the risk of network congestion.
STIG Date
Microsoft Exchange Server 2003 2014-08-19

Details

Check Text ( C-22406r1_chk )
Access the SMTP Maximum Hop Count configuration.

Procedure: Exchange System Manager >> Administrative Groups >> [administrative group] >> Servers >> [Server] >> Protocols >> SMTP >> [specific SMTP server] >> properties >> Delivery tab >> Advanced button

The “Enter maximum hop count” value should be 30.

Criteria: If the “Enter maximum hop count” value is 30, this is not a finding.
Fix Text (F-19334r1_fix)
Set the maximum hop count value.

Procedure: Exchange System Manager >> administrative groups >> [administrative group] >> Servers >> [Server] >> Protocols >> SMTP >> [specific SMTP server] >> properties >> Delivery tab >> advanced button.

For "Enter maximum hop count", enter 30.